Application requirements for vehicle-to-everything applications

ABSTRACT

Apparatuses, methods, and systems are disclosed for obtaining application requirements for vehicle-to-everything applications. One method (1000) includes receiving (1002) at least one application requirement from at least one vehicle-to-everything application. The method (1000) includes receiving (1004) at least one provisioning parameter, wherein the at least one provisioning parameter is determined for a plurality of vehicle-to-everything user equipments based on the at least one application requirement, and the plurality of vehicle-to-everything user equipments are serviced by a plurality of communication networks.

FIELD

The subject matter disclosed herein relates generally to wirelesscommunications and more particularly relates to application requirementsfor vehicle-to-everything applications.

BACKGROUND

The following abbreviations are herewith defined, at least some of whichare referred to within the following description: Third GenerationPartnership Project (“3GPP”), 5^(th) Generation (“5G”), 5G System(“5GS”), 5G QoS Identifiers (“5QIs”), Authentication, Authorization, andAccounting (“AAA”), Positive-Acknowledgment (“ACK”), ApplicationFunction (“AF”), Authentication and Key Agreement (“AKA”), AggregationLevel (“AL”), Access and Mobility Management Function (“AMF”), Angle ofArrival (“AoA”), Angle of Departure (“AoD”), Access Point (“AP”), AccessStratum (“AS”), Application Service Provider (“ASP”), Autonomous Uplink(“AUL”), Authentication Server Function (“AUSF”), Authentication Token(“AUTN”), Background Data (“BD”), Background Data Transfer (“BDT”), BeamFailure Detection (“BFD”), Beam Failure Recovery (“BFR”), Binary PhaseShift Keying (“BPSK”), Base Station (“BS”), Buffer Status Report(“BSR”), Bandwidth (“BW”), Bandwidth Part (“BWP”), Cell RNTI (“C-RNTI”),Carrier Aggregation (“CA”), Channel Access Priority Class (“CAPC”),Channel Busy Ratio (“CBR”), Contention-Based Random Access (“CBRA”),Clear Channel Assessment (“CCA”), Common Control Channel (“CCCH”),Control Channel Element (“CCE”), Cyclic Delay Diversity (“CDD”), CodeDivision Multiple Access (“CDMA”), Control Element (“CE”),Contention-Free Random Access (“CFRA”), Configured Grant (“CG”),Closed-Loop (“CL”), Coordinated Multipoint (“CoMP”), Category ofRequirements (“CoR”), Channel Occupancy Time (“COT”), Cyclic Prefix(“CP”), Cyclical Redundancy Check (“CRC”), Channel State Information(“CSI”), Channel State Information-Reference Signal (“CSI-RS”), CommonSearch Space (“CSS”), Control Resource Set (“CORESET”), Discrete FourierTransform Spread (“DFTS”), Downlink Control Information (“DCI”),Downlink Feedback Information (“DFI”), Downlink (“DL”), DemodulationReference Signal (“DMRS”), Data Network Name (“DNN”), Data Radio Bearer(“DRB”), Discontinuous Reception (“DRX”), Dedicated Short-RangeCommunications (“DSRC”), Downlink Pilot Time Slot (“DwPTS”), EnhancedClear Channel Assessment (“eCCA”), Enhanced Mobile Broadband (“eMBB”),Evolved Node B (“eNB”), Enhanced V2X (“eV2X”), Extensible AuthenticationProtocol (“EAP”), Effective Isotropic Radiated Power (“EIRP”), EvolvedPacket System (“EPS”), European Telecommunications Standards Institute(“ETSI”), Frame Based Equipment (“FBE”), Frequency Division Duplex(“FDD”), Frequency Division Multiplexing (“FDM”), Frequency DivisionMultiple Access (“FDMA”), Frequency Division Orthogonal Cover Code(“FD-OCC”), Frequency Range 1—sub 6 GHz frequency bands and/or 410 MHzto 7125 MHz (“FR1”), Frequency Range 2—24.25 GHz to 52.6 GHz (“FR2”),Universal Geographical Area Description (“GAD”), Guaranteed Bit Rate(“GBR”), Group Leader (“GL”), 5G Node B or Next Generation Node B(“gNB”), Global Navigation Satellite System (“GNSS”), General PacketRadio Services (“GPRS”), Guard Period (“GP”), Global Positioning System(“GPS”), Generic Public Subscription Identifier (“GPSI”), Global Systemfor Mobile Communications (“GSM”), Globally Unique Temporary UEIdentifier (“GUTI”), Home AMF (“hAMF”), Hybrid Automatic Repeat Request(“HARQ”), Home Location Register (“HLR”), Handover (“HO”), Home PLMN(“HPLMN”), Home Subscriber Server (“HSS”), Hash Expected Response(“HXRES”), Identity or Identifier (“ID”), Information Element (“IE”),International Mobile Equipment Identity (“IMEI”), International MobileSubscriber Identity (“IMSI”), International Mobile Telecommunications(“IMT”), Internet-of-Things (“IoT”), Intelligent Transportation Systems(“ITS”), Key Performance Indicator (“KPI”), Layer 1 (“L1”), Layer 2(“L2”), Layer 3 (“L3”), Licensed Assisted Access (“LAA”), Local AreaData Network (“LADN”), Local Area Network (“LAN”), Load Based Equipment(“LBE”), Listen-Before-Talk (“LBT”), Logical Channel (“LCH”), LogicalChannel Group (“LCG”), Logical Channel Prioritization (“LCP”),Log-Likelihood Ratio (“LLR”), Level of Automation (“LoA”), Line of Sight(“LOS”), Long Term Evolution (“LTE”), LTE Vehicle (“LTE-V”), MultipleAccess (“MA”), Medium Access Control (“MAC”), Multimedia BroadcastMulticast Services (“MBMS”), Maximum Bit Rate (“MBR”), MinimumCommunication Range (“MCR”), Modulation Coding Scheme (“MCS”), MobileEdge Computing (“MEC”), Master Information Block (“MIB”), Multiple InputMultiple Output (“MIMO”), Mobility Management (“MM”), MobilityManagement Entity (“MME”), Mobile Network Operator (“MNO”), MobileOriginated (“MO”), massive MTC (“mMTC”), Maximum Power Reduction(“MPR”), Machine Type Communication (“MTC”), Multi User Shared Access(“MUSA”), Non Access Stratum (“NAS”), Narrowband (“NB”),Negative-Acknowledgment (“NACK”) or (“NAK”), New Data Indicator (“NDI”),Network Entity (“NE”), Network Exposure Function (“NEF”), NetworkExposure Function/Service Capability Exposure Function (“NEF/SCEF”),Network Function (“NE”), Non-LOS (“NLOS”), Next Generation (“NG”), NG 5GS-TMSI (“NG-5G-S-TMSI”), Non-Orthogonal Multiple Access (“NOMA”), NewRadio (“NR”), NR Unlicensed (“NR-U”), Network Repository Function(“NRF”), Network Scheduled Mode (“NS Mode”) (e.g., network scheduledmode of V2X communication resource allocation—Mode-1 in NR V2X andMode-3 in LTE V2X), Network Slice Instance (“NSI”), Network SliceSelection Assistance Information (“NSSAI”), Network Slice SelectionFunction (“NSSF”), Network Slice Selection Policy (“NSSP”), Operation,Administration, and Maintenance System or Operation and MaintenanceCenter (“OAM”), Orthogonal Frequency Division Multiplexing (“OFDM”),Open-Loop (“OL”), Other System Information (“OSI”), Power AngularSpectrum (“PAS”), Physical Broadcast Channel (“PBCH”), Power Control(“PC”), UE to UE interface (“PC5”), Policy and Charging Control (“PCC”),Primary Cell (“PCell”), Policy and Charging Rules Function (“PCRF”),Policy Control Function (“PCF”), Physical Cell Identity (“PCI”),Physical Downlink Control Channel (“PDCCH”), Packet Data ConvergenceProtocol (“PDCP”), Packet Data Network Gateway (“PGW”), PhysicalDownlink Shared Channel (“PDSCH”), Pattern Division Multiple Access(“PDMA”), Packet Data Unit (“PDU”), Physical Hybrid ARQ IndicatorChannel (“PHICH”), Power Headroom (“PH”), Power Headroom Report (“PHR”),Physical Layer (“PHY”), Public Land Mobile Network (“PLMN”), Prose PerPacket Priority (“PPPP”), Prose Per Packet Reliability (“PPPR”), PC5 5QI(“PQIs”), Physical Random Access Channel (“PRACH”), Physical ResourceBlock (“PRB”), Proximity Services (“ProSe”), Positioning ReferenceSignal (“PRS”), Physical Sidelink Control Channel (“PSCCH”), PrimarySecondary Cell (“PSCell”), Physical Sidelink Feedback Control Channel(“PSFCH”), Physical Uplink Control Channel (“PUCCH”), Physical UplinkShared Channel (“PUSCH”), QoS Class Identifier (“QCI”), Quasi Co-Located(“QCL”), Quality of Service (“QoS”), Quadrature Phase Shift Keying(“QPSK”), Registration Area (“RA”), RA RNTI (“RA-RNTI”), Radio AccessNetwork (“RAN”), Random (“RAND”), Radio Access Technology (“RAT”),Serving RAT (“RAT-1”) (serving with respect to Uu), Other RAT (“RAT-2”)(non-serving with respect to Uu), Random Access Procedure (“RACH”),Random Access Preamble Identifier (“RAPID”), Random Access Response(“RAR”), Resource Block Assignment (“RBA”), Resource Element Group(“REG”), Radio Link Control (“RLC”), RLC Acknowledged Mode (“RLC-AM”),RLC Unacknowledged Mode/Transparent Mode (“RLC-UM/TM”), Radio LinkFailure (“RLF”), Radio Link Monitoring (“RLM”), Radio Network TemporaryIdentifier (“RNTI”), Reference Signal (“RS”), Remaining Minimum SystemInformation (“RMSI”), Radio Resource Control (“RRC”), Radio ResourceManagement (“RRM”), Resource Spread Multiple Access (“RSMA”), ReferenceSignal Received Power (“RSRP”), Received Signal Strength Indicator(“RSSI”), Round Trip Time (“RTT”), Receive (“RX”), Service CapabilityExposure Function (“SCEF”), Sparse Code Multiple Access (“SCMA”),Scheduling Request (“SR”), Sounding Reference Signal (“SRS”), SingleCarrier Frequency Division Multiple Access (“SC-FDMA”), Secondary Cell(“SCell”), Secondary Cell Group (“SCG”), Shared Channel (“SCH”),Sidelink Control Information (“SCI”), Sub-carrier Spacing (“SCS”),Service Data Unit (“SDU”), Security Anchor Function (“SEAF”), ServiceEnabler Architecture Layer (“SEAL”), Sidelink Feedback ContentInformation (“SFCI”), Serving Gateway (“SGW”), System Information Block(“SIB”), SystemInformationBlockType1 (“SIB1”),SystemInformationBlockType2 (“SIB2”), Subscriber Identity/IdentificationModule (“SIM”), Signal-to-Interference-Plus-Noise Ratio (“SINR”),Sidelink (“SL”), Service Level Agreement (“SLA”), SidelinkSynchronization Signals (“SLSS”), Session Management (“SM”), SessionManagement Function (“SMF”), Special Cell (“SpCell”), Single NetworkSlice Selection Assistance Information (“S-NSSAI”), Scheduling Request(“SR”), Signaling Radio Bearer (“SRB”), Shortened TMSI (“S-TMSI”),Shortened TTI (“sTTI”), Synchronization Signal (“SS”), Sidelink CSI RS(“S-CSI RS”), Sidelink PRS (“S-PRS”), Sidelink SSB (“S-SSB”),Synchronization Signal Block (“SSB”), Subscription Concealed Identifier(“SUCI”), Scheduling User Equipment (“SUE”), Supplementary Uplink(“SUL”), Subscriber Permanent Identifier (“SUPI”), Tracking Area (“TA”),TA Identifier (“TAI”), TA Update (“TAU”), Timing Alignment Timer(“TAT”), Transport Block (“TB”), Transport Block Size (“TBS”),Time-Division Duplex (“TDD”), Time Division Multiplex (“TDM”), TimeDivision Orthogonal Cover Code (“TD-OCC”), Temporary Mobile SubscriberIdentity (“TMSI”), Time of Flight (“ToF”), Transmission Power Control(“TPC”), Transmission Reception Point (“TRP”), Transmission TimeInterval (“TTI”), Transmit (“TX”), Uplink Control Information (“UCI”),Unified Data Management Function (“UDM”), Unified Data Repository(“UDR”), User Entity/Equipment (Mobile Terminal) (“UE”) (e.g., a V2XUE), UE Autonomous Mode (UE autonomous selection of V2X communicationresource—e.g., Mode-2 in NR V2X and Mode-4 in LTE V2X. UE autonomousselection may or may not be based on a resource sensing operation),Uplink (“UL”), UL SCH (“UL-SCH”), Universal Mobile TelecommunicationsSystem (“UMTS”), User Plane (“UP”), UP Function (“UPF”), Uplink PilotTime Slot (“UpPTS”), Ultra-reliability and Low-latency Communications(“URLLC”), UE Route Selection Policy (“URSP”), Vehicle-to-Vehicle(“V2V”), Vehicle-to-Everything (“V2X”), V2X Control Function (“V2XCF”),V2X UE (e.g., a UE capable of vehicular communication using 3GPPprotocols), V2X Application Enabler (“VAE”), Visiting AMY (“vAMF”),Visiting NSSF (“vNSSF”), Visiting PLMN (“VPLMN”), Wide Area Network(“WAN”), and Worldwide Interoperability for Microwave Access (“WiMAX”).

In certain wireless communications networks, vehicle-to-everythingapplications may be used.

BRIEF SUMMARY

Methods for obtaining application requirements for vehicle-to-everythingapplications are disclosed. Apparatuses and systems also perform thefunctions of the methods. One embodiment of a method includes obtainingat least one application requirement from at least onevehicle-to-everything application. In some embodiments, the methodincludes determining at least one provisioning parameter for a pluralityof vehicle-to-everything user equipments based on the at least oneapplication requirement, wherein the plurality of vehicle-to-everythinguser equipments are serviced by a plurality of communication networks.In various embodiments, the method includes transmitting the at leastone provisioning parameter to at least one vehicle-to-everything userequipment of the plurality of vehicle-to-everything user equipments, atleast one communication network of the plurality of communicationnetworks, or some combination thereof.

One apparatus for obtaining application requirements forvehicle-to-everything applications includes a processor that: obtains atleast one application requirement from at least onevehicle-to-everything application; and determines at least oneprovisioning parameter for a plurality of vehicle-to-everything userequipments based on the at least one application requirement, whereinthe plurality of vehicle-to-everything user equipments are serviced by aplurality of communication networks. In certain embodiments, theapparatus includes a transmitter that transmits the at least oneprovisioning parameter to at least one vehicle-to-everything userequipment of the plurality of vehicle-to-everything user equipments, atleast one communication network of the plurality of communicationnetworks, or some combination thereof.

In certain embodiments, a method for receiving application requirementsfor vehicle-to-everything applications includes receiving at least oneapplication requirement from at least one vehicle-to-everythingapplication. In some embodiments, the method includes receiving at leastone provisioning parameter, wherein the at least one provisioningparameter is determined for a plurality of vehicle-to-everything userequipments based on the at least one application requirement, and theplurality of vehicle-to-everything user equipments are serviced by aplurality of communication networks.

In various embodiments, an apparatus for receiving applicationrequirements for vehicle-to-everything applications includes a receiverthat: receives at least one application requirement from at least onevehicle-to-everything application; and receives at least oneprovisioning parameter, wherein the at least one provisioning parameteris determined for a plurality of vehicle-to-everything user equipmentsbased on the at least one application requirement, and the plurality ofvehicle-to-everything user equipments are serviced by a plurality ofcommunication networks.

BRIEF DESCRIPTION OF THE DRAWINGS

A more particular description of the embodiments briefly described abovewill be rendered by reference to specific embodiments that areillustrated in the appended drawings. Understanding that these drawingsdepict only some embodiments and are not therefore to be considered tobe limiting of scope, the embodiments will be described and explainedwith additional specificity and detail through the use of theaccompanying drawings, in which:

FIG. 1 is a schematic block diagram illustrating one embodiment of awireless communication system for obtaining and/or receiving applicationrequirements for vehicle-to-everything applications;

FIG. 2 is a schematic block diagram illustrating one embodiment of anapparatus that may be used for receiving application requirements forvehicle-to-everything applications;

FIG. 3 is a schematic block diagram illustrating one embodiment of anapparatus that may be used for obtaining application requirements forvehicle-to-everything applications;

FIG. 4 is a schematic block diagram illustrating one embodiment of asystem for obtaining and/or receiving application requirements forvehicle-to-everything applications;

FIG. 5 is a diagram illustrating one embodiment of communications forupdating application requirements;

FIG. 6 is a diagram illustrating another embodiment of communicationsfor updating application requirements;

FIG. 7 is a diagram illustrating a further embodiment of communicationsfor updating application requirements;

FIG. 8 is a diagram illustrating yet another embodiment ofcommunications for updating application requirements;

FIG. 9 is a flow chart diagram illustrating one embodiment of a methodfor obtaining application requirements for vehicle-to-everythingapplications; and

FIG. 10 is a flow chart diagram illustrating one embodiment of a methodfor receiving application requirements for vehicle-to-everythingapplications.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art, aspects of theembodiments may be embodied as a system, apparatus, method, or programproduct. Accordingly, embodiments may take the form of an entirelyhardware embodiment, an entirely software embodiment (includingfirmware, resident software, micro-code, etc.) or an embodimentcombining software and hardware aspects that may all generally bereferred to herein as a “circuit,” “module” or “system.” Furthermore,embodiments may take the form of a program product embodied in one ormore computer readable storage devices storing machine readable code,computer readable code, and/or program code, referred hereafter as code.The storage devices may be tangible, non-transitory, and/ornon-transmission. The storage devices may not embody signals. In acertain embodiment, the storage devices only employ signals foraccessing code.

Certain of the functional units described in this specification may belabeled as modules, in order to more particularly emphasize theirimplementation independence. For example, a module may be implemented asa hardware circuit comprising custom very-large-scale integration(“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such aslogic chips, transistors, or other discrete components. A module mayalso be implemented in programmable hardware devices such as fieldprogrammable gate arrays, programmable array logic, programmable logicdevices or the like.

Modules may also be implemented in code and/or software for execution byvarious types of processors. An identified module of code may, forinstance, include one or more physical or logical blocks of executablecode which may, for instance, be organized as an object, procedure, orfunction. Nevertheless, the executables of an identified module need notbe physically located together, but may include disparate instructionsstored in different locations which, when joined logically together,include the module and achieve the stated purpose for the module.

Indeed, a module of code may be a single instruction, or manyinstructions, and may even be distributed over several different codesegments, among different programs, and across several memory devices.Similarly, operational data may be identified and illustrated hereinwithin modules, and may be embodied in any suitable form and organizedwithin any suitable type of data structure. The operational data may becollected as a single data set, or may be distributed over differentlocations including over different computer readable storage devices.Where a module or portions of a module are implemented in software, thesoftware portions are stored on one or more computer readable storagedevices.

Any combination of one or more computer readable medium may be utilized.The computer readable medium may be a computer readable storage medium.The computer readable storage medium may be a storage device storing thecode. The storage device may be, for example, but not limited to, anelectronic, magnetic, optical, electromagnetic, infrared, holographic,micromechanical, or semiconductor system, apparatus, or device, or anysuitable combination of the foregoing.

More specific examples (a non-exhaustive list) of the storage devicewould include the following: an electrical connection having one or morewires, a portable computer diskette, a hard disk, a random access memory(“RAM”), a read-only memory (“ROM”), an erasable programmable read-onlymemory (“EPROM” or Flash memory), a portable compact disc read-onlymemory (“CD-ROM”), an optical storage device, a magnetic storage device,or any suitable combination of the foregoing. In the context of thisdocument, a computer readable storage medium may be any tangible mediumthat can contain, or store a program for use by or in connection with aninstruction execution system, apparatus, or device.

Code for carrying out operations for embodiments may be any number oflines and may be written in any combination of one or more programminglanguages including an object oriented programming language such asPython, Ruby, Java, Smalltalk, C++, or the like, and conventionalprocedural programming languages, such as the “C” programming language,or the like, and/or machine languages such as assembly languages. Thecode may execute entirely on the user's computer, partly on the user'scomputer, as a stand-alone software package, partly on the user'scomputer and partly on a remote computer or entirely on the remotecomputer or server. In the latter scenario, the remote computer may beconnected to the user's computer through any type of network, includinga local area network (“LAN”) or a wide area network (“WAN”), or theconnection may be made to an external computer (for example, through theInternet using an Internet Service Provider).

Reference throughout this specification to “one embodiment,” “anembodiment,” or similar language means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment. Thus, appearances of the phrases“in one embodiment,” “in an embodiment,” and similar language throughoutthis specification may, but do not necessarily, all refer to the sameembodiment, but mean “one or more but not all embodiments” unlessexpressly specified otherwise. The terms “including,” “comprising,”“having,” and variations thereof mean “including but not limited to,”unless expressly specified otherwise. An enumerated listing of itemsdoes not imply that any or all of the items are mutually exclusive,unless expressly specified otherwise. The terms “a,” “an,” and “the”also refer to “one or more” unless expressly specified otherwise.

Furthermore, the described features, structures, or characteristics ofthe embodiments may be combined in any suitable manner. In the followingdescription, numerous specific details are provided, such as examples ofprogramming, software modules, user selections, network transactions,database queries, database structures, hardware modules, hardwarecircuits, hardware chips, etc., to provide a thorough understanding ofembodiments. One skilled in the relevant art will recognize, however,that embodiments may be practiced without one or more of the specificdetails, or with other methods, components, materials, and so forth. Inother instances, well-known structures, materials, or operations are notshown or described in detail to avoid obscuring aspects of anembodiment.

Aspects of the embodiments are described below with reference toschematic flowchart diagrams and/or schematic block diagrams of methods,apparatuses, systems, and program products according to embodiments. Itwill be understood that each block of the schematic flowchart diagramsand/or schematic block diagrams, and combinations of blocks in theschematic flowchart diagrams and/or schematic block diagrams, can beimplemented by code. The code may be provided to a processor of ageneral purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions, which execute via the processor of the computer orother programmable data processing apparatus, create means forimplementing the functions/acts specified in the schematic flowchartdiagrams and/or schematic block diagrams block or blocks.

The code may also be stored in a storage device that can direct acomputer, other programmable data processing apparatus, or other devicesto function in a particular manner, such that the instructions stored inthe storage device produce an article of manufacture includinginstructions which implement the function/act specified in the schematicflowchart diagrams and/or schematic block diagrams block or blocks.

The code may also be loaded onto a computer, other programmable dataprocessing apparatus, or other devices to cause a series of operationalsteps to be performed on the computer, other programmable apparatus orother devices to produce a computer implemented process such that thecode which execute on the computer or other programmable apparatusprovide processes for implementing the functions/acts specified in theflowchart and/or block diagram block or blocks.

The schematic flowchart diagrams and/or schematic block diagrams in theFigures illustrate the architecture, functionality, and operation ofpossible implementations of apparatuses, systems, methods and programproducts according to various embodiments. In this regard, each block inthe schematic flowchart diagrams and/or schematic block diagrams mayrepresent a module, segment, or portion of code, which includes one ormore executable instructions of the code for implementing the specifiedlogical function(s).

It should also be noted that, in some alternative implementations, thefunctions noted in the block may occur out of the order noted in theFigures. For example, two blocks shown in succession may, in fact, beexecuted substantially concurrently, or the blocks may sometimes beexecuted in the reverse order, depending upon the functionalityinvolved. Other steps and methods may be conceived that are equivalentin function, logic, or effect to one or more blocks, or portionsthereof, of the illustrated Figures.

Although various arrow types and line types may be employed in theflowchart and/or block diagrams, they are understood not to limit thescope of the corresponding embodiments. Indeed, some arrows or otherconnectors may be used to indicate only the logical flow of the depictedembodiment. For instance, an arrow may indicate a waiting or monitoringperiod of unspecified duration between enumerated steps of the depictedembodiment. It will also be noted that each block of the block diagramsand/or flowchart diagrams, and combinations of blocks in the blockdiagrams and/or flowchart diagrams, can be implemented by specialpurpose hardware-based systems that perform the specified functions oracts, or combinations of special purpose hardware and code.

The description of elements in each figure may refer to elements ofproceeding figures. Like numbers refer to like elements in all figures,including alternate embodiments of like elements.

FIG. 1 depicts an embodiment of a wireless communication system 100 forobtaining and/or receiving application requirements forvehicle-to-everything applications. In one embodiment, the wirelesscommunication system 100 includes remote units 102, network units 104,and one or more V2X application units 105. Even though a specific numberof remote units 102, network units 104, and V2X application units 105are depicted in FIG. 1 , one of skill in the art will recognize that anynumber of remote units 102, network units 104, and V2X application units105 may be included in the wireless communication system 100.

In one embodiment, the remote units 102 may include computing devices,such as desktop computers, laptop computers, personal digital assistants(“PDAs”), tablet computers, smart phones, smart televisions (e.g.,televisions connected to the Internet), set-top boxes, game consoles,security systems (including security cameras), vehicle on-boardcomputers, network devices (e.g., routers, switches, modems), aerialvehicles, drones, or the like. In some embodiments, the remote units 102include wearable devices, such as smart watches, fitness bands, opticalhead-mounted displays, or the like. Moreover, the remote units 102 maybe referred to as subscriber units, mobiles, mobile stations, users,terminals, mobile terminals, fixed terminals, subscriber stations, UE,user terminals, a device, or by other terminology used in the art. Theremote units 102 may communicate directly with one or more of thenetwork units 104 via UL communication signals. In certain embodiments,the remote units 102 may communicate directly with other remote units102 via sidelink communication.

The network units 104 may be distributed over a geographic region. Incertain embodiments, a network unit 104 may also be referred to as anaccess point, an access terminal, a base, a base station, a Node-B, aneNB, a gNB, a Home Node-B, a relay node, a device, a core network, anaerial server, a radio access node, an AP, NR, a network entity, an AMF,a UDM, a UDR, a UDM/UDR, a PCF, a RAN, an NSSF, or by any otherterminology used in the art. The network units 104 are generally part ofa radio access network that includes one or more controllerscommunicably coupled to one or more corresponding network units 104. Theradio access network is generally communicably coupled to one or morecore networks, which may be coupled to other networks, like the Internetand public switched telephone networks, among other networks. These andother elements of radio access and core networks are not illustrated butare well known generally by those having ordinary skill in the art.

In one implementation, the wireless communication system 100 iscompliant with NR protocols standardized in 3GPP, wherein the networkunit 104 transmits using an OFDM modulation scheme on the DL and theremote units 102 transmit on the UL using a SC-FDMA scheme or an OFDMscheme. More generally, however, the wireless communication system 100may implement some other open or proprietary communication protocol, forexample, WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants,CDMA2000, Bluetooth®, ZigBee, Sigfoxx, among other protocols. Thepresent disclosure is not intended to be limited to the implementationof any particular wireless communication system architecture orprotocol.

The network units 104 may serve a number of remote units 102 within aserving area, for example, a cell or a cell sector via a wirelesscommunication link. The network units 104 transmit DL communicationsignals to serve the remote units 102 in the time, frequency, and/orspatial domain. In certain embodiments, the V2X application unit 105 mayprovide application requirements to the remote unit 102 and/or thenetwork unit 104.

In various embodiments, a network unit 104 may obtain at least oneapplication requirement from at least one vehicle-to-everythingapplication. In some embodiments, the network unit 104 may determine atleast one provisioning parameter for a plurality ofvehicle-to-everything user equipments based on the at least oneapplication requirement, wherein the plurality of vehicle-to-everythinguser equipments are serviced by a plurality of communication networks.In various embodiments, the network unit 104 may transmit the at leastone provisioning parameter to at least one vehicle-to-everything userequipment of the plurality of vehicle-to-everything user equipments, atleast one communication network of the plurality of communicationnetworks, or some combination thereof. Accordingly, the network unit 104may be used for obtaining application requirements forvehicle-to-everything applications.

In certain embodiments, a remote unit 102 may receive at least oneapplication requirement from at least one vehicle-to-everythingapplication. In some embodiments, the remote unit 102 may receive atleast one provisioning parameter, wherein the at least one provisioningparameter is determined for a plurality of vehicle-to-everything userequipments based on the at least one application requirement, and theplurality of vehicle-to-everything user equipments are serviced by aplurality of communication networks. Accordingly, the remote unit 102may be used for receiving application requirements forvehicle-to-everything applications.

FIG. 2 depicts one embodiment of an apparatus 200 that may be used forreceiving application requirements for vehicle-to-everythingapplications. The apparatus 200 includes one embodiment of the remoteunit 102. Furthermore, the remote unit 102 may include a processor 202,a memory 204, an input device 206, a display 208, a transmitter 210, anda receiver 212. In some embodiments, the input device 206 and thedisplay 208 are combined into a single device, such as a touchscreen. Incertain embodiments, the remote unit 102 may not include any inputdevice 206 and/or display 208. In various embodiments, the remote unit102 may include one or more of the processor 202, the memory 204, thetransmitter 210, and the receiver 212, and may not include the inputdevice 206 and/or the display 208.

The processor 202, in one embodiment, may include any known controllercapable of executing computer-readable instructions and/or capable ofperforming logical operations. For example, the processor 202 may be amicrocontroller, a microprocessor, a central processing unit (“CPU”), agraphics processing unit (“GPU”), an auxiliary processing unit, a fieldprogrammable gate array (“FPGA”), or similar programmable controller. Insome embodiments, the processor 202 executes instructions stored in thememory 204 to perform the methods and routines described herein. Theprocessor 202 is communicatively coupled to the memory 204, the inputdevice 206, the display 208, the transmitter 210, and the receiver 212.

The memory 204, in one embodiment, is a computer readable storagemedium. In some embodiments, the memory 204 includes volatile computerstorage media. For example, the memory 204 may include a RANI, includingdynamic RANI (“DRAM”), synchronous dynamic RANI (“SDRAM”), and/or staticRAM (“SRAM”). In some embodiments, the memory 204 includes non-volatilecomputer storage media. For example, the memory 204 may include a harddisk drive, a flash memory, or any other suitable non-volatile computerstorage device. In some embodiments, the memory 204 includes bothvolatile and non-volatile computer storage media. In some embodiments,the memory 204 also stores program code and related data, such as anoperating system or other controller algorithms operating on the remoteunit 102.

The input device 206, in one embodiment, may include any known computerinput device including a touch panel, a button, a keyboard, a stylus, amicrophone, or the like. In some embodiments, the input device 206 maybe integrated with the display 208, for example, as a touchscreen orsimilar touch-sensitive display. In some embodiments, the input device206 includes a touchscreen such that text may be input using a virtualkeyboard displayed on the touchscreen and/or by handwriting on thetouchscreen. In some embodiments, the input device 206 includes two ormore different devices, such as a keyboard and a touch panel.

The display 208, in one embodiment, may include any known electronicallycontrollable display or display device. The display 208 may be designedto output visual, audible, and/or haptic signals. In some embodiments,the display 208 includes an electronic display capable of outputtingvisual data to a user. For example, the display 208 may include, but isnot limited to, an LCD display, an LED display, an OLED display, aprojector, or similar display device capable of outputting images, text,or the like to a user. As another, non-limiting, example, the display208 may include a wearable display such as a smart watch, smart glasses,a heads-up display, or the like. Further, the display 208 may be acomponent of a smart phone, a personal digital assistant, a television,a table computer, a notebook (laptop) computer, a personal computer, avehicle dashboard, or the like.

In certain embodiments, the display 208 includes one or more speakersfor producing sound. For example, the display 208 may produce an audiblealert or notification (e.g., a beep or chime). In some embodiments, thedisplay 208 includes one or more haptic devices for producingvibrations, motion, or other haptic feedback. In some embodiments, allor portions of the display 208 may be integrated with the input device206. For example, the input device 206 and display 208 may form atouchscreen or similar touch-sensitive display. In other embodiments,the display 208 may be located near the input device 206.

The transmitter 210 is used to provide UL communication signals to thenetwork unit 104 and the receiver 212 is used to receive DLcommunication signals from the network unit 104, as described herein. Insome embodiments, the receiver 212: receives at least one applicationrequirement from at least one vehicle-to-everything application; andreceives at least one provisioning parameter, wherein the at least oneprovisioning parameter is determined for a plurality ofvehicle-to-everything user equipments based on the at least oneapplication requirement, and the plurality of vehicle-to-everything userequipments are serviced by a plurality of communication networks.

Although only one transmitter 210 and one receiver 212 are illustrated,the remote unit 102 may have any suitable number of transmitters 210 andreceivers 212. The transmitter 210 and the receiver 212 may be anysuitable type of transmitters and receivers. In one embodiment, thetransmitter 210 and the receiver 212 may be part of a transceiver.

FIG. 3 depicts one embodiment of an apparatus 300 that may be used forobtaining application requirements for vehicle-to-everythingapplications. The apparatus 300 includes one embodiment of the networkunit 104. Furthermore, the network unit 104 may include a processor 302,a memory 304, an input device 306, a display 308, a transmitter 310, anda receiver 312. As may be appreciated, the processor 302, the memory304, the input device 306, the display 308, the transmitter 310, and thereceiver 312 may be substantially similar to the processor 202, thememory 204, the input device 206, the display 208, the transmitter 210,and the receiver 212 of the remote unit 102, respectively.

In certain embodiments, the processor 302 may: obtain at least oneapplication requirement from at least one vehicle-to-everythingapplication; and determine at least one provisioning parameter for aplurality of vehicle-to-everything user equipments based on the at leastone application requirement, wherein the plurality ofvehicle-to-everything user equipments are serviced by a plurality ofcommunication networks. In some embodiments, the transmitter 310transmits the at least one provisioning parameter to at least onevehicle-to-everything user equipment of the plurality ofvehicle-to-everything user equipments, at least one communicationnetwork of the plurality of communication networks, or some combinationthereof. Although only one transmitter 310 and one receiver 312 areillustrated, the network unit 104 may have any suitable number oftransmitters 310 and receivers 312. The transmitter 310 and the receiver312 may be any suitable type of transmitters and receivers. In oneembodiment, the transmitter 310 and the receiver 312 may be part of atransceiver.

In some embodiments, there may be PC5 parameter provisioning andconfiguration to a group of V2X users that directly communicate viasidelink communication. In such embodiments, one or more group membersof the group of V2X users are registered to different PLMNs.

In various embodiments, V2X services may have ultra-reliable and lowlatency characteristics and/or may require high data rates due to highexpected payloads. CoR and/or LoA may be used, may reflect technologicalfunctional aspects, and/or may affect system performance requirementsfor different V2X configurations.

As may be appreciated, CoRs may include: general aspects; vehicleplatooning; advanced driving; extended sensors; and/or remote driving.Moreover, LoAs may include: no automation; driver assistance; partialautomation; conditional automation; high automation; and/or fullautomation.

In certain embodiments, each CoR scenario and/or each degree of LoA,requirement may be specified in terms of: payload (e.g., bytes);transmission rate (e.g., message/sec); maximum end-to-end latency (e.g.,ms); reliability (e.g., %); data rate (e.g., Mbps); and/or minimumrequired communication range (e.g., meters). In some embodiments, V2Xscenarios may be delay and reliability critical while a rate (e.g., andthus a resource) requirement may vary for each CoR and/or LoA becausethey may support different payloads (e.g., from 300 bytes to 12,000bytes) under a strict delay requirement. In various embodiments,different CoR and/or LoA combinations may use provisioning of QoS and/orradio parameters (e.g., even for the same V2X application—such asplatooning).

In certain embodiments, a V2X communication may be in a multi-operatorenvironment because it may not be possible to ensure that only oneoperator will offer a V2X service. Such multi-operator environments mayinclude multi-PLMN roaming and/or non-roaming configurations.

In some embodiments, such as in non-roaming configurations,communication may be among V2X UEs registered to different PLMNs forexchanging advanced driving and/or safety-related messages. As usedherein, a V2X UE may include one or more of the following: 1) one ormore applications related to one or more V2X services; 2) one or moreapplications acting as middleware clients; and/or 3) a communicationentity. In such embodiments, radio resources for communication may beeither operator-managed (e.g., FR1 and FR2 spectrum bands may be usedfor 5G V2X services) or not managed by an operator (e.g. ITSbands—licensed frequency band of 5.9 GHz (5.85 GHz-5.925 GHz)).Moreover, in such embodiments, if more than one network providesassistance in a control plane (e.g., semi-persistent and/or dynamicscheduling of SL resources by a BS, provisioning of SL radio parametersby a PCF and/or a V2XCF), coordination between involved PLMNs may bedone. Further, in such embodiments, network-assisted V2X may besupported in both EPS and 5GS (e.g., denoted as Mode-3 for LTE-V, andMode-1 for 5GS).

In certain embodiments, three multi-PLMN scenarios may be used for thefollowing V2X services: 1) RAN sharing; 2) multi-PLMN V2X serviceoffering; and/or 3) regional roaming. In such embodiments, multipleoperators may selectively coordinate offering of V2X services. Thecoordination of multiple operators may relate to spectrum resources usedfor delivering V2V services and respective configurations. In variousembodiments, a UE may acquire V2V configurations: 1) by reading SIBs ofnon-serving PLMNs; 2) via pre-configuration; 3) by serving eNB signaling(e.g., SIBs from a serving PLMN); and/or 4) from a V2X server.

In some embodiments, coordination options may be inadequate for one ormore of the following reasons: 1) a network operator does not shareinformation for provisioning parameters provided for V2X users to othernetwork operators, especially if operator managed resources are used(e.g., assumed in 5G-V2X scenarios); 2) setting of PC5 parameters mayrequire involvement of one or more V2X application servers that provideV2X service requirements to a network (e.g., for a single-operator case,a network may translate service requirements to a network provisioningparameters; however, configuration of PC5 parameters for amulti-operator V2X service may use coordination between an applicationserver and all involved PLMNs); 3) a V2X server may not be aware of PC5provisioning parameters that include resource and QoS parameters (e.g.,this may use an enablement layer to provide translation of the PC5provisioning parameters to service provisioning parameters and viceversa, or the exposure of PC5 parameters from the network to the V2Xserver); 4) different provisioning may be used for a given LoA for oneV2X service and a LoA may be changed while the service is running (e.g.,a coordination among operators may be dynamic and/or may includedifferent combinations of parameters based on adapted applicationrequirements); and/or a V2X service may run for UEs that are connectedto different PLMNs with different RAT capabilities (e.g., 5G, LTE). Insuch scenarios, coordination between PLMNs may use more complexinteractions that may be undertaken by an application layer (e.g., inLTE-V, a V2XCF may provide provisioning for a PC5, and, in 5GS, a PCFmay provide provisioning for the PC5).

In various embodiments, an application layer may support eV2X services.In certain embodiments, a V2X application enabler layer may be used tofacilitate efficient use and/or deployment of V2X services over 3GPPsystems. In such embodiments, the V2X application enabler layer mayinclude a VAE server that may be PLMN-owned, a 3rd party server, avertical server, and/or one or more VAE clients at a vehicle side. Insome embodiments, a VAE server may be a middleware platform thatprovides support functionalities to enabler clients and/or may interactwith application specific servers (e.g., a platooning server) aninvolved PLMNs to facilitate meeting per vertical requirements. Incertain embodiments, a VAE server may use SEAL services that may includecommon support functionalities for all verticals. In such embodiments,the VAE server may be co-located with SEAL servers.

Table 1 shows one embodiment of multi-PLMN coordination.

TABLE 1 Multi-PLMN Support by Application Enabler Layer The V2Xcommunication may be multi operator environment since it is not possibleto ensure that only one operator will offer the V2X service. Basicsafety critical services or advanced driving assistance applications asplatooning are some examples of V2X services that may be in multiplePLMN environments. The involvement of an AF in multi-PLMN interactionsmay be possible via N33 and T8. In this regard, AF may support efficientinterworking of multiple PLMNs in non-roaming scenarios by communicatingwith multiple NEFs and NEF + SCEF via N33 and T8. The VAE server, actingas AF, may be capable of receiving network & QoS parameters from one ormultiple PLMNs, as well as receiving application requirements from oneor multiple application servers. Hence, VAE server could support somemulti-PLMN interactions in the above scenarios (e.g. by configuringQoS/network parameters on behalf of underlying PLMNs). The applicationlayer functional model and VAE layer capabilities may be enhanced tosupport multi-PLMN interactions.

In various embodiments: 1) an initial configuration of PC5 parameters inmulti-PLMN scenarios may be used; and/or 2) an adaptation of aconfiguration of PC5 parameters may be based on application-triggered ornetwork-triggered changes.

In certain embodiments, PC5 provisioning and coordinated configurationin multi-operator network-assisted V2X scenarios may be controlled by amiddleware application entity. In some embodiments, a middlewareapplication entity may include the following: 1) receiving input (e.g.,application requirements) from one or more V2X application servers(e.g., the application requirements may include one or more of thefollowing: a) a multi-PLMN service indication, b) a level ofcoordination and/or granularity, c) PLMN priorities, d) a KPI and/or aQoS per session, e) an application to service mapping, f) useridentifiers, g) PLMN ids, h) a service area and/or a geographical area,i) assistance information (e.g., traffic conditions, weather, maps,etc.), and/or j) a service to LoA mapping); 2) receiving input from oneor more applications and/or clients of one or more V2X UEs that includeat least one of the following: a PC5 status, PC5 measurements, PC5analytics, a PC5 discovery indication, an out of coverage indication, anout of coverage expectation, CBR measurements, and/or UE contextinformation; 3) a new functionality at the middleware entity fordetermining coordinated provisioning parameters for PC5 communicationfor one or more V2V multi-operator sessions for a V2X service area(e.g., the provisioning parameters may be an initial coordinatedprovisioning configuration and/or an adaptation of the coordinatedprovisioning due to application updated requirements or PC5 conditionchanges); 4) sending to one or more applications and/or clients of theone or more V2X UEs the coordinated provisioning parameters for PC5(e.g., radio parameters, PC5 policy parameters, and so forth); and/or 5)sending to one or more networks the provisioning parameters for therespective UEs via N33 and/or T8 (e.g., from an AF). As used herein, N33may be a reference point between an NEF and an AF. Moreover, T8 may be areference point between an SCEF and an application server or an AF.

FIG. 4 is a schematic block diagram illustrating one embodiment of asystem 400 for obtaining and/or receiving application requirements forvehicle-to-everything applications. The system 400 includes a firstvehicle 402 (e.g., V2X vehicle), a second vehicle 404 (e.g., V2Xvehicle), a first PLMN 406, a second PLMN 408, an application (“App”)enabler server 410 (e.g., middleware application entity), a first V2Xserver 412, and a second V2X server 414. Furthermore, the first vehicle402 includes a first V2X application 416, a second V2X application 418,an application enabler client 420, and a 3GPP UE 422. Moreover, thesecond vehicle 404 includes a first V2X application 424, a second V2Xapplication 426, an application enabler client 428, and a 3GPP UE 430.The application enabler client 420 of the first vehicle 402 communicatesvia a communication link 432 with the application enabler server 410.The 3GPP UE 422 of the first vehicle 402 may communicate via acommunication link 434 with the 3GPP UE 430 of the second vehicle 404.Further, the 3GPP UE 422 of the first vehicle 402 communicates via acommunication link 436 with the first PLMN 406. Moreover, the first PLMN406 communicates via a communication link 438 (e.g., N33, T8) with theapplication enabler server 410. The application enabler client 428 ofthe second vehicle 404 communicates via a communication link 440 withthe application enabler server 410. Further, the 3GPP UE 430 of thesecond vehicle 404 communicates via a communication link 442 with thesecond PLMN 408. Moreover, the second PLMN 408 communicates via acommunication link 444 (e.g., N33, T8) with the application enablerserver 410. In addition, the first V2X server 412 communicates via acommunication link 446 with the application enabler server 410. Thesecond V2X server 414 communicates via a communication link 448 with theapplication enabler server 410.

In some embodiments, an initial provisioning may be performed as soon asUEs are authorized to use PC5 per PLMN. In such embodiments, anadditional provisioning may be used at a middleware for ensuring thatprovisioning of radio parameters is coordinated among operators involvedat a PC5 session.

In various embodiments, an initial provisioning of parameters (e.g.,coordinated provisioning of parameters) may be provided by anapplication enabler server to V2X UEs. The initial provisioning mayinclude at least one of the following: 1) radio parameters (e.g.,includes the radio parameters per PC5 RAT (e.g., LTE PC5, NR PC5) withgeographical areas and an indication of whether they are operatormanaged or non-operator managed); 2) a policy and/or parameters per RATfor PC5 TX profile selection; 3) a policy and/or parameters that includesetting of PPPP and/or PPPR if LTE PC5 is selected; 4) a policy and/orparameters if NR PC5 is selected (e.g., NR PC5 QoS mapping configurationmay be per flow due to NR PC5 using a bearer concept and LTE PC5 mayhave per packet QoS handling); 5) AS layer configurations; 6) a timevalidity; 7) a multi-PLMN V2X service flag and/or notification; 8) aconfiguration of TX and/or RX resource pools per V2X service type orgeographical area; 9) radio parameters for joint utilization permulti-PLMN V2X service; 10) a list of available PC5 5QIs (or PQIs) perPLMN; 11) a joint PC5 QoS mapping configuration; 11) an allowed PLMNlist and capabilities for joint radio resource utilization; 12) a PLMNpriority over joint resources; 13) a service-to-LoA indication; and/or14) a geographical area for the initial provisioning.

In certain embodiments, an initial provisioning requiresapplication-related information from one or more V2X servers thatindicate information such as: provisioning parameters per PLMN,information from V2X UEs regarding a PC5 status, information from V2XUEs regarding measurements, information from V2X UEs regardinganalytics, a PC5 discovery indication, an out of coverage expectation,an out of coverage indication, CBR measurements, and/or UE contextinformation.

In some embodiments, an initial trigger for additional provisioning maycome from a V2X server and/or a V2X application enabler client at a UEthat wants to establish a PC5 connection with users that belong todifferent PLMNs.

In various embodiments, a mechanism for applying provisioning parametersafter coordination may either be sent to involved networks to update PCCrules (e.g., to a PCF for 5GS or to a PCRF for EPS) by an AF (e.g., AFrequest to PCF) or by a UE to update the policy (e.g., UE policy updaterequest to an AMF and/or a PCF).

In certain embodiments, an adaptation of an initial provisioning ofparameters (e.g., updated provisioning configuration) may be performedafter a V2X UE or an application server captures a change that mayresult in a change of the initial provisioning of parameters (e.g., PC5provisioning parameters). In such embodiments, the updated provisioningconfiguration may be used by middleware to facilitate setting of radioparameters coordinated among operators involved in a PC5 session.

In some embodiments, an updated provisioning configuration (e.g.,reconfiguration of the initial provisioning of parameters) may beprovided by a middleware server to V2X UEs and may include one or moreof the following: 1) radio parameters (e.g., includes the radioparameters per PC5 RAT (e.g., LTE PC5, NR PC5) with geographical areasand an indication of whether they are operator managed or non-operatormanaged); 2) a policy and/or parameters per RAT for PC5 TX profileselection; 3) a policy and/or parameters that include setting of PPPPand/or PPPR if LTE PC5 is selected; 4) a policy and/or parameters if NRPC5 is selected (e.g., NR PC5 QoS mapping configuration may be per flowdue to NR PC5 using a bearer concept and LTE PC5 may have per packet QoShandling); 5) AS layer configurations; 6) a time validity; 7) ageographical area for the provisioning; 8) a multi-PLMN V2X service flagand/or notification; 9) a configuration of TX and/or RX resource poolsper V2X service type or geographical area; 10) radio parameters forjoint utilization per multi-PLMN V2X service; 11) a list of availablePQIs per PLMN; 12) a joint PC5 QoS mapping configuration; 13) an allowedPLMN list and capabilities for joint radio resource utilization; 14) aPLMN priority over the joint resources; 15) a service-to-LoA indicationand/or mapping; 16) delta parameters from the initial provisioning;and/or 17) a cause for the provisioning adaptation (e.g., 1. PC5 QoS,resource, and/or availability change, 2. LoA change, 3. group formationadaptation, 4. traffic congestion in a service area, and so forth).

In various embodiments, a reconfiguration requires application-relatedinformation from one or more V2X servers that indicate information suchas: provisioning parameters per PLMN, information from V2X UEs regardinga PC5 status, information from V2X UEs regarding measurements,information from V2X UEs regarding analytics, a PC5 discoveryindication, an out of coverage expectation, an out of coverageindication, CBR measurements, and/or UE context information.

In certain embodiments, a PC5 radio configuration change may occur dueto change of load, channel conditions, expected congestions, one or moreapplication adaptation (e.g., change of LoA, group formation, servicecoverage, service range). In some embodiments, an application server oran application of one or more UEs may trigger an adaptation (e.g.,reconfiguration) based on a type of change (e.g., a PC5 status changemay be triggered by a UE).

In a first embodiment, there may be triggering by a V2X server and/orprovisioning via an AF request to a PCF for involved PLMNs.

In the first embodiment, an enabler server (e.g., a VAE server and/orSEAL server) provides a configuration (e.g., or reconfiguration) bycoordinating policies and/or radio parameters for multiple PLMNs. In thefirst embodiment, a trigger for functionality activation may be arequirement from a V2X server (e.g., a V2X server that has all availableprovisioning information per PLMN). In some embodiments, a VAE clientand/or SEAL client may provide to a VAE server information about a PC5status and/or conditions to facilitate giving an awareness at an enablerserver to capture a PC5 resource situation (e.g., load of radioresources, congestion, LOS and/or NLOS conditions, interference, PC5 QoSmonitoring) to enable deciding a multi-PLMN configuration and/orreconfiguration (e.g., this may be resource restrictions and/or joinresource allocation). In such embodiments, coordinated provisioning maybe applied via an AF request for service parameter provisioning from aPCF and/or PCRF.

FIG. 5 is a diagram illustrating one embodiment of communications 500for updating application requirements. The communications 500 arebetween a first V2X vehicle 502, a second V2X vehicle 504, a first PLMN506, a second PLMN 508, a VAE server 510 (e.g., or middleware entity, anapplication enabler server, a SEAL server), and a V2X specific server512. The first V2X vehicle 502 includes a first V2X application 514, afirst enabler client 516, and a first UE 518. Moreover, the second V2Xvehicle 504 includes a second UE 520, a second enabler client 522, and asecond V2X application 524. As may be appreciated, any of thecommunications 500 described herein may include one or more messages.

In some embodiments, the first UE 518 and the second UE 520 may beauthorized 526 for PC5 communications with the first PLMN 506 and thesecond PLMN 508 via communications between various devices,respectively.

In a first communication 528 transmitted from the V2X specific server512 to the VAE server 510, the V2X specific server 512 sends anapplication requirement message to the VAE server 510. The applicationrequirement message may provide to the VAE server 510 a requirement forperforming coordinated provisioning for V2X services that span more thanone PLMN, and may also provide information related to a per PLMNconfiguration and/or policies. The application requirement message mayinclude one or more of the following parameters: one or more V2X UEidentifications (e.g., GPSI, external ID); a V2X service ID; PLMN IDs; atransaction ID; a group ID for a group of UEs (e.g., for groupcastand/or broadcast scenario); radio parameters; a policy and/or parametersper RAT for PC5 TX profile selection; a policy and/or parameters if LTEPC5 is selected; a policy and/or parameters if NR PC5 is selected; ASlayer configurations; a multi-PLMN V2X service flag and/or notification;a level of coordination and PLMN info; a V2X service to LoA indication;a time validity and/or geographical area for a provisioning requirement;and/or a cause for a provisioning adaptation (e.g., 1. PC5 QoS,resource, and/or availability change, 2. LoA change, 3. group formationadaptation, 4. traffic congestion in a service area, and so forth).

In a second communication 530 transmitted from the VAE server 510 to thesecond enabler client 522 and in a third communication 532 transmittedfrom the VAE server 510 to the first enabler client 516, the VAE server510 sends a PC5 monitoring request message to the second and firstenabler clients 522 and 516 (e.g., VAE clients and/or SEAL clients ofaffected V2X UEs) corresponding to the UE IDs provided in the firstcommunication 528. The PC5 monitoring request message may include the UEIDs, service ID, radio parameters to monitor (e.g., request for CBRmeasurements, averaged channel conditions, load indication, and soforth), a policy and/or parameters monitoring request (e.g., per RAT),and/or UE context information.

In a fourth communication 534 transmitted from the second UE 520 to thesecond enabler client 522 and in a fifth communication 536 transmittedfrom the first UE 518 to the first enabler client 516, the first andsecond UEs 518 and 520 transmit to the second and first enabler clients522 and 516 (e.g., VAE clients and/or SEAL client of the affected V2XUEs) from the AS layer of the first and second UEs 518 and 520 L1/L2measurements as well as policies and/or parameters per RAT and UEcontext information as requested in the second and third communications530 and 532.

In a sixth communication 538 transmitted from the second enabler client522 to the VAE server 510 and in a seventh communication 540 transmittedfrom the first enabler client 516 to the VAE server 510, the second andfirst enabler clients 522 and 516 (e.g., VAE client and/or SEAL clientsof affected V2X UEs) send a PC5 monitoring response and/or reportmessage to the VAE server 510 which indicates at least one of thefollowing: radio measurements which may be CSI, RRM, RLM, and/or CBRmeasurements or an abstracted and/or averaged version of the radiomeasurements; up-to-date information on a policy and/or parameters(e.g., PQI attributes, a communication range, a RAT availability, a RATpreference, and so forth); and/or PC5 related events (e.g., a PC5unavailability, LOS and/or NLOS conditions, a request for morebandwidth, an inter-session interference indication, a PC5 QoS expecteddowngrade, moving out of PLMN coverage, and so forth).

In certain embodiments, the VAE Server 510 derives 542 a coordinated PC5provisioning configuration that takes into account the information frommultiple PLMNs. Certain criterion for selecting updated polices andradio parameters may be to ensure meeting KPIs for all involved PC5sessions in a given service and/or geographical area (e.g., set in thefirst communication 528) while efficiently utilizing the radio resourcesin multi-PLMN environments. In some embodiments, such as for operatormanaged resources, some restrictions of usage of resources may play arole on the decisions.

In an eighth communication 544 transmitted from the VAE server 510 tothe first PLMN 506 and in a ninth communication 546 transmitted from theVAE server 510 to the second PLMN 508, the VAE server 510 acts as an AFand creates 548 an AF request to perform a service parameterprovisioning procedure with the PCFs and/or PCRFs in both the first andsecond PLMNs 506 and 508. The eighth and ninth communications 544 and546 may include a request message (e.g.,Nnef_serviceparameter_create_Req). Service provisioning parameters forthe service provisioning procedure include certain predeterminedparameters (e.g., radio and/or policy parameters that may be provided bythe V2X specific server 512) and one or more of the following: UE IDs,an application ID, a V2X server ID, an AF ID, a multi-PLMN V2X serviceflag and/or notification, radio parameters for joint utilization permulti-PLMN V2X service, a list of available PQIs per PLMN, a joint PC5QoS mapping configuration, an allowed PLMN list and capabilities forjoint radio resource utilization, a PLMN priority over joint resources,a service-to-LoA indication, a geographical area for the provisioning,delta parameters from the initial provisioning, and/or a cause forprovisioning adaptation (e.g., 1. PC5 QoS, resource, and/or availabilitychange, 2. an LoA change, 3. A group formation adaptation, 4. A trafficcongestion in a service area, and so forth).

In a tenth communication 550 transmitted from the second PLMN 508 to theVAE server 510 and in an eleventh communication 552 transmitted from thefirst PLMN 506 to the VAE server 510, the second and first PLMNs 508 and506 transmit a response message (e.g.,Nnef_service_parameter_create_Response) to the VAE server 510.

In a twelfth communication 554 transmitted from the VAE server 510 tothe V2X specific server 512, the VAE server 510 sends a notification tothe V2X specific server 512 to inform the V2X specific server 512 of thefulfilment of the provisioning configuration.

In certain embodiments, the UE policy updates are made 556 with the newprovisioning policies. In various embodiments, PC5 establishment isperformed 558.

In a second embodiment, there may be triggering by a V2X server and/orprovisioning via UE policy provisioning.

In the second embodiment, an enabler server (e.g., a VAE server and/orSEAL server) provides a configuration (e.g., or reconfiguration) bycoordinating policies and/or radio parameters for multiple PLMNs. In thesecond embodiment, a trigger for functionality activation may be arequirement from a V2X server (e.g., a V2X server that has all theavailable provisioning information per PLMN). In some embodiments, a VAEclient and/or SEAL client may provide to a VAE server information abouta PC5 status and/or conditions to facilitate giving an awareness at theenabler server to capture a PC5 resource situation to enable deciding ona multi-PLMN configuration and/or reconfiguration. In such embodiments,coordinated provisioning may be applied via UE policy provisioningsignaling from one or more of UEs to an AMF and/or PCF.

FIG. 6 is a diagram illustrating another embodiment of communications600 for updating application requirements. The communications 600 arebetween a first V2X vehicle 602, a second V2X vehicle 604, a first PLMN606, a second PLMN 608, a VAE server 610 (e.g., or middleware entity, anapplication enabler server, a SEAL server), and a V2X specific server612. The first V2X vehicle 602 includes a first V2X application 614, afirst enabler client 616, and a first UE 618. Moreover, the second V2Xvehicle 604 includes a second UE 620, a second enabler client 622, and asecond V2X application 624. As may be appreciated, any of thecommunications 600 described herein may include one or more messages.

In some embodiments, the first UE 618 and the second UE 620 may beauthorized 626 for PC5 communications with the first PLMN 606 and thesecond PLMN 608 via communications between various devices,respectively.

In a first communication 628 transmitted from the V2X specific server612 to the VAE server 610, the V2X specific server 612 sends anapplication requirement message to the VAE server 610. The applicationrequirement message may provide to the VAE server 610 a requirement forperforming coordinated provisioning for V2X services that span more thanone PLMN, and may also provide information related to a per PLMNconfiguration and/or policies. The application requirement message mayinclude one or more of the following parameters: one or more V2X UEidentifications (e.g., GPSI, external ID); a V2X service ID; PLMN IDs; atransaction ID; a group ID for a group of UEs (e.g., for groupcastand/or broadcast scenario); radio parameters; a policy and/or parametersper RAT for PC5 TX profile selection; a policy and/or parameters if LTEPC5 is selected; a policy and/or parameters if NR PC5 is selected; ASlayer configurations; a multi-PLMN V2X service flag and/or notification;a level of coordination and PLMN info; a V2X service to LoA indication;a time validity and/or geographical area for a provisioning requirement;and/or a cause for a provisioning adaptation (e.g., 1. PC5 QoS,resource, and/or availability change, 2. LoA change, 3. group formationadaptation, 4. traffic congestion in a service area, and so forth).

In a second communication 630 transmitted from the VAE server 610 to thesecond enabler client 622 and in a third communication 632 transmittedfrom the VAE server 610 to the first enabler client 616, the VAE server610 sends a PC5 monitoring request message to the second and firstenabler clients 622 and 616 (e.g., VAE clients and/or SEAL clients ofaffected V2X UEs) corresponding to the UE IDs provided in the firstcommunication 628. The PC5 monitoring request message may include the UEIDs, service ID, radio parameters to monitor (e.g., request for CBRmeasurements, averaged channel conditions, load indication, and soforth), a policy and/or parameters monitoring request (e.g., per RAT),and/or UE context information.

In a fourth communication 634 transmitted from the second UE 620 to thesecond enabler client 622 and in a fifth communication 636 transmittedfrom the first UE 618 to the first enabler client 616, the first andsecond UEs 618 and 620 transmit to the second and first enabler clients622 and 616 (e.g., VAE clients and/or SEAL client of the affected V2XUEs) from the AS layer of the first and second UEs 618 and 620 L1/L2measurements as well as policies and/or parameters per RAT and UEcontext information as requested in the second and third communications630 and 632.

In a sixth communication 638 transmitted from the second enabler client622 to the VAE server 610 and in a seventh communication 640 transmittedfrom the first enabler client 616 to the VAE server 610, the second andfirst enabler clients 622 and 616 (e.g., VAE clients and/or SEAL clientsof affected V2X UEs) send a PC5 monitoring response and/or reportmessage to the VAE server 610 which indicates at least one of thefollowing: radio measurements which may be CSI, RRM, RLM, and/or CBRmeasurements or an abstracted and/or averaged version of the radiomeasurements; up-to-date information on a policy and/or parameters(e.g., PQI attributes, a communication range, a RAT availability, a RATpreference, and so forth); and/or PC5 related events (e.g., a PC5unavailability, LOS and/or NLOS conditions, a request for morebandwidth, an inter-session interference indication, a PC5 QoS expecteddowngrade, moving out of PLMN coverage, and so forth).

In certain embodiments, the VAE Server 610 derives 642 a coordinated PC5provisioning configuration that takes into account the information frommultiple PLMNs. Certain criterion for selecting updated polices andradio parameters may be to ensure meeting KPIs for all involved PC5sessions in a given service and/or geographical area (e.g., set in thefirst communication 628) while efficiently utilizing the radio resourcesin multi-PLMN environments. In some embodiments, such as for operatormanaged resources, some restrictions of usage of resources may play arole on the decisions.

In an eighth communication 644 transmitted from the VAE server 610 tothe first enabler client 616 and in a ninth communication 646transmitted from the VAE server 610 to the second enabler client 622,the VAE server 610 sends a coordinated PC5 provisioning request messageto the first and second enabler clients 616 and 622 to provide updatedparameters. Service provisioning parameters for the PC5 provisioningrequest message include certain predetermined parameters (e.g., radioand/or policy parameters that may be provided by the V2X specific server612) and one or more of the following: UE IDs, an application ID, a V2Xserver ID, an AF ID, a multi-PLMN V2X service flag and/or notification,radio parameters for joint utilization per multi-PLMN V2X service, alist of available PQIs per PLMN, a joint PC5 QoS mapping configuration,an allowed PLMN list and capabilities for joint radio resourceutilization, a PLMN priority over joint resources, a service-to-LoAindication, a geographical area for the provisioning, delta parametersfrom the initial provisioning, and/or a cause for provisioningadaptation (e.g., 1. PC5 QoS, resource, and/or availability change, 2.an LoA change, 3. A group formation adaptation, 4. A traffic congestionin a service area, and so forth).

In a tenth communication 648 transmitted from the first enabler client616 to the first UE 618 and in an eleventh communication 650 transmittedfrom the second enabler client 622 to the second UE 620, the first andsecond enabler clients 616 and 618 (e.g., VAE clients and/or SEALclients) provide the PC5 provisioning request message to an AS layer ofthe affected V2X-UEs (e.g., the first UE 618 and the second UE 620) totrigger 652 a UE policy configuration (e.g., the first UE 618 to thefirst PLMN 606 (e.g., PCF) and the second UE 620 to the second PLMN 608(e.g., PCF)).

In a twelfth communication 654 transmitted from the first enabler client616 to the VAE server 610 and in a thirteenth communication 656transmitted from the second enabler client 622 to the VAE server 610,the first and second enabler clients 616 and 622 (e.g., one or more VAEclients and/or SEAL clients) send a coordinated PC5 provisioningresponse message to the VAE server 610 (e.g., a respective VAE serverand/or SEAL server) to notify the VAE server 610 of the result (e.g.,ACK/NACK, positive or negative acknowledgement) based on the tenth andeleventh communications 648 and 650.

In a fourteenth communication 658 transmitted from the VAE server 610 tothe V2X specific server 612, the VAE server 610 sends a notification tothe V2X specific server 612 to inform the V2X specific server 612 of thefulfilment of the provisioning configuration.

In a third embodiment, there may be triggering by a V2X UE, aconfiguration by an enabler server, and/or provisioning via either anAF, a PCF, and/or a UE Policy

In the third embodiment, the trigger for functionality activation may bea requirement from an application of the V2X-UE. In various embodiments,an enabler server (e.g., VAE server and/or SEAL server) may provide aconfiguration (e.g., or reconfiguration) by coordinating policies and/orradio parameters for multiple PLMNs based on a trigger by a UE. In suchembodiments, coordinated policy provisioning execution may happen eithervia an AF request to a PCF and/or a PCRF or via UE policy provisioning.

FIG. 7 is a diagram illustrating a further embodiment of communications700 for updating application requirements. The communications 700 arebetween a first V2X vehicle 702, a second V2X vehicle 704, a first PLMN706, a second PLMN 708, a VAE server 710 (e.g., or middleware entity, anapplication enabler server, a SEAL server), and a V2X specific server712. The first V2X vehicle 702 includes a first V2X application 714, afirst enabler client 716, and a first UE 718. Moreover, the second V2Xvehicle 704 includes a second UE 720, a second enabler client 722, and asecond V2X application 724. As may be appreciated, any of thecommunications 700 described herein may include one or more messages.

In some embodiments, the first UE 718 and the second UE 720 may beauthorized 726 for PC5 communications with the first PLMN 706 and thesecond PLMN 708 via communications between various devices,respectively.

In various embodiments, the VAE server 710 may have received 728 V2Xprovisioning and/or parameters per PLMN from the V2X specific server712.

In a first communication 730 transmitted from the first V2X application714 to the first enabler client 716, the first V2X application 714 sendsan application requirement message to the first enabler client 716. Theapplication requirement message may provide to the first enabler client716 a requirement for performing coordinated provisioning for V2Xservices that span more than one PLMN, and may also provide informationrelated to a per PLMN configuration and/or policies. The applicationrequirement message may include one or more of the following parameters:one or more V2X UE identifications (e.g., GPSI, external ID); a V2Xservice ID; PLMN IDs; a transaction ID; a group ID for a group of UEs(e.g., for groupcast and/or broadcast scenario); radio parameters; apolicy and/or parameters per RAT for PC5 TX profile selection; a policyand/or parameters if LTE PC5 is selected; a policy and/or parameters ifNR PC5 is selected; AS layer configurations; a multi-PLMN V2X serviceflag and/or notification; a level of coordination and PLMN info; a V2Xservice to LoA indication; a time validity and/or geographical area fora provisioning requirement; and/or a cause for a provisioning adaptation(e.g., 1. PC5 QoS, resource, and/or availability change, 2. LoA change,3. group formation adaptation, 4. traffic congestion in a service area,and so forth).

In a second communication 732 transmitted from the first enabler client716 to the VAE server 710, the first enabler client 716 sends acoordinated PC5 provisioning request message to the VAE server 710 torequest that the VAE server 710 coordinate provisioning parameterstaking into account the VAE server 710 awareness on all involved perPLMN provisioning. Service provisioning parameters for the PC5provisioning request message may include one or more of the following:UE IDs, a group ID, an application ID, a V2X server ID, an AF ID, aservice ID, a PC5 session ID, a transaction ID, a multi-PLMN V2X serviceflag and/or notification, a level of coordination requirement (e.g.,radio parameters, a policy per RAT, parameters per RAT), locationinformation, radio parameters for joint utilization per multi-PLMN V2Xservice, a list of available PQIs per PLMN, a joint PC5 QoS mappingconfiguration, an allowed PLMN list and capabilities for joint radioresource utilization, a PLMN priority over joint resources, aservice-to-LoA indication, group information (e.g., members, formation),a geographical area for the provisioning, delta parameters from theinitial provisioning, and/or a cause for provisioning adaptation(e.g., 1. PC5 QoS, resource, and/or availability change, 2. an LoAchange, 3. a group formation adaptation, 4. a traffic congestion in aservice area, and so forth).

In a third communication 734 transmitted from the VAE server 710 to thefirst enabler client 716, the VAE server 710 sends a PC5 provisioningcoordination response message to the first enabler client 716 to notifythe first enabler client 716 of the result (e.g., ACK/NACK, positive ornegative acknowledgement).

In a fourth communication 736 transmitted from the VAE server 710 to thesecond enabler client 722, the VAE server 710 optionally sends a PC5monitoring request message to the second enabler client 722. The PC5monitoring request message may include the UE IDs, service ID, radioparameters to monitor (e.g., request for CBR measurements, averagedchannel conditions, load indication, and so forth), a policy and/orparameters monitoring request (e.g., per RAT), and/or UE contextinformation.

In a fifth communication 738 transmitted from the second enabler client722 to the VAE server 710, the second enabler client 722 (e.g., VAEclient and/or SEAL client of affected V2X UEs) receives from an AS layerof the second UE 720 measurements as well as policies and/or parametersper RAT and UE context information, and the second enabler client 722sends a PC5 monitoring response and/or report message to the VAE server710 which indicates at least one of the following: radio measurementswhich may be CSI, RRM, RLM, and/or CBR measurements or an abstractedand/or averaged version of the radio measurements; up-to-dateinformation on a policy and/or parameters (e.g., PQI attributes, acommunication range, a RAT availability, a RAT preference, and soforth); and/or PC5 related events (e.g., a PC5 unavailability, LOSand/or NLOS conditions, a request for more bandwidth, an inter-sessioninterference indication, a PC5 QoS expected downgrade, moving out ofPLMN coverage, and so forth).

The VAE server 710 derives 740 the coordinated PC5 provisioningconfiguration that takes into account information from multiple PLMNs.Certain criterion for selecting updated polices and radio parameters maybe to ensure meeting KPIs for all involved PC5 sessions in a givenservice and/or geographical area (e.g., set in the first communication728) while efficiently utilizing the radio resources in multi-PLMNenvironments. In some embodiments, such as for operator managedresources, some restrictions of usage of resources may play a role onthe decisions.

Depending on the provisioning execution (e.g., AF trigger or UEtrigger), the following steps 742: 1) Option 1: for AF-basedprovisioning communications 544 through 554 of FIG. 5 may be completed;and 2) Option 2: for UE policy provisioning communications 644 through658 of FIG. 6 may be completed.

In a fourth embodiment, there may be PC5 conditions and/or a statusupdate at a V2X UE, reconfiguration by a middleware server, and/orre-provisioning via a UE policy provisioning.

In this fourth embodiment, a trigger for functionality activation may bea change at a PC5 status and/or conditions monitored by an applicationenabler client. In various embodiments, an enabler server (e.g., VAEserver and/or SEAL server) may provide a configuration (e.g., orreconfiguration) by coordinating policies and/or radio parameters formultiple PLMNs based on a trigger by a UE. In such embodiments,coordinated policy provisioning execution may happen either via an AFrequest to a PCF and/or a PCRF or via UE policy provisioning.

FIG. 8 is a diagram illustrating yet another embodiment ofcommunications 800 for updating application requirements. Thecommunications 800 are between a first V2X vehicle 802, a second V2Xvehicle 804, a first PLMN 806, a second PLMN 808, a VAE server 810(e.g., or middleware entity, an application enabler server, a SEALserver), and a V2X specific server 812. The first V2X vehicle 802includes a first V2X application 814, a first enabler client 816, and afirst UE 818. Moreover, the second V2X vehicle 804 includes a second UE820, a second enabler client 822, and a second V2X application 824. Asmay be appreciated, any of the communications 800 described herein mayinclude one or more messages.

In some embodiments, the first UE 818 and the second UE 820 may beauthorized 826 for PC5 communications with the first PLMN 806 and thesecond PLMN 808 via communications between various devices,respectively.

In various embodiments, the VAE server 810 may have received 828 V2Xprovisioning and/or parameters per PLMN from the V2X specific server812.

In a first communication 830 transmitted from the first UE 818 to thefirst enabler client 816, the first UE 818 may send a PC5 QoS and/orresource availability change event message to the first enabler client816. The change event may provide information about possible PC5 QoSdegradation, a conflicts indication, and/or an interference indicationin one or more radio resource pools and/or a change of LoS conditions.

In a second communication 832 transmitted from the first enabler client816 to the VAE server 810, the first enabler client 816 sends a PC5provisioning adaptation request message to the VAE server 810 to requestthat the VAE server 810 coordinate provisioning parameters taking intoaccount the VAE server 810 awareness on all involved per PLMNprovisioning. Service provisioning parameters for the PC5 provisioningadaptation request message may include one or more of the following: UEIDs, a group ID, an application ID, a V2X server ID, an AF ID, a serviceID, a PC5 session ID, a transaction ID, a multi-PLMN V2X service flagand/or notification, a level of coordination requirement (e.g., radioparameters, a policy per RAT, parameters per RAT), location information,radio parameters for joint utilization per multi-PLMN V2X service, alist of available PQIs per PLMN, a joint PC5 QoS mapping configuration,an allowed PLMN list and capabilities for joint radio resourceutilization, a PLMN priority over joint resources, a service-to-LoAindication, group information (e.g., members, formation), a geographicalarea for the provisioning, delta parameters from the initialprovisioning, and/or a cause for provisioning adaptation (e.g., 1. PC5QoS, resource, and/or availability change, 2. an LoA change, 3. a groupformation adaptation, 4. a traffic congestion in a service area, and soforth).

In a third communication 834 transmitted from the VAE server 810 to thesecond enabler client 822, the VAE server 810 optionally sends a PC5monitoring request message to the second enabler client 822. The PC5monitoring request message may include the UE IDs, service ID, radioparameters to monitor (e.g., request for CBR measurements, averagedchannel conditions, load indication, and so forth), a policy and/orparameters monitoring request (e.g., per RAT), and/or UE contextinformation.

In a fourth communication 836 transmitted from the second enabler client822 to the VAE server 810, the second enabler client 822 (e.g., VAEclient and/or SEAL client of affected V2X UEs) receives from an AS layerof the second UE 820 measurements as well as policies and/or parametersper RAT and UE context information, and the second enabler client 822sends a PC5 monitoring response and/or report message to the VAE server810 which indicates at least one of the following: radio measurementswhich may be CSI, RRM, RLM, and/or CBR measurements or an abstractedand/or averaged version of the radio measurements; up-to-dateinformation on a policy and/or parameters (e.g., PQI attributes, acommunication range, a RAT availability, a RAT preference, and soforth); and/or PC5 related events (e.g., a PC5 unavailability, LOSand/or NLOS conditions, a request for more bandwidth, an inter-sessioninterference indication, a PC5 QoS expected downgrade, moving out ofPLMN coverage, and so forth).

The VAE server 810 derives 838 the coordinated PC5 provisioningconfiguration that takes into account information from multiple PLMNs.Certain criterion for selecting updated polices and radio parameters maybe to ensure meeting KPIs for all involved PC5 sessions in a givenservice and/or geographical area (e.g., set in the second communication832) while efficiently utilizing the radio resources in multi-PLMNenvironments. In some embodiments, such as for operator managedresources, some restrictions of usage of resources may play a role onthe decisions.

In a fifth communication 840 transmitted from the VAE server 810 to thefirst enabler client 816, the VAE server 810 sends a PC5 provisioningadaptation response message to the first enabler client 816 to notifythe first enabler client 816 of the result (e.g., ACK/NACK, positive ornegative acknowledgement).

Depending on the provisioning execution (e.g., AF trigger or UEtrigger), the following steps 842: 1) Option 1: for AF-basedprovisioning communications 544 through 554 of FIG. 5 may be completed;and 2) Option 2: for UE policy provisioning communications 644 through658 of FIG. 6 may be completed.

FIG. 9 is a flow chart diagram illustrating one embodiment of a method900 for obtaining application requirements for vehicle-to-everythingapplications. In some embodiments, the method 900 is performed by anapparatus, such as the network unit 104. In certain embodiments, themethod 900 may be performed by a processor executing program code, forexample, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliaryprocessing unit, a FPGA, or the like.

In various embodiments, the method 900 includes obtaining 902 at leastone application requirement from at least one vehicle-to-everythingapplication. In some embodiments, the method 900 includes determining904 at least one provisioning parameter for a plurality ofvehicle-to-everything user equipments based on the at least oneapplication requirement, wherein the plurality of vehicle-to-everythinguser equipments are serviced by a plurality of communication networks.In various embodiments, the method 900 includes transmitting 906 the atleast one provisioning parameter to at least one vehicle-to-everythinguser equipment of the plurality of vehicle-to-everything userequipments, at least one communication network of the plurality ofcommunication networks, or some combination thereof.

In certain embodiments, the at least one application requirementcomprises a user equipment identifier, a radio parameter, a policyparameter, a public land mobile network identifier, a multiple publicland mobile network vehicle-to-everything service indication, a level ofcoordination, a level of granularity, a public land mobile networkpriority, a key performance indicator per vehicle-to-everything session,a quality of service per vehicle-to-everything session, anapplication-to-service mapping, a service area, a geographical area,assistance information, a service-to-level of automation mapping, orsome combination thereof. In some embodiments, the at least onevehicle-to-everything application comprises a vehicle-to-everythingapplication server, a vehicle-to-everything application client of avehicle-to-everything user equipment of the plurality ofvehicle-to-everything user equipments, or a combination thereof.

In various embodiments, the at least one provisioning parametercomprises a radio parameter, a policy per radio access technology, aparameter per radio access technology, a policy for a long termevolution network, a policy for a new radio network, an access stratumlayer configuration, a time validity, a geographical area, a multiplepublic land mobile network vehicle-to-everything service flag, amultiple public land mobile network vehicle-to-everything servicenotification, a resource pool configuration per vehicle-to-everythingservice type, a resource pool configuration per vehicle-to-everythinggeographical area, a radio parameter for joint utilization per multiplepublic land mobile network vehicle-to-everything service, a list ofavailable quality indicators per public land mobile network, a qualityof service mapping configuration, an allowed public land mobile networklist and capabilities for joint radio resource utilization, a publicland mobile network priority over joint resources, a service-to-level ofautomation mapping, a delta parameter, a cause for provisioningadaptation, or some combination thereof. In one embodiment, the at leastone provisioning parameter comprises an initial configuration for theplurality of vehicle-to-everything user equipments.

In certain embodiments, the at least one provisioning parametercomprises an updated configuration for the plurality ofvehicle-to-everything user equipments. In some embodiments, the updatedconfiguration is triggered by an adaptation of the at least oneapplication requirement, a sidelink communication requirement, or acombination thereof. In various embodiments, the at least oneprovisioning parameter is provided to at least one application client ofthe at least one vehicle-to-everything user equipment.

In one embodiment, the at least one provisioning parameter is providedto the at least one communication network via user plane signaling,control plane signaling, or a combination thereof. As used herein, userplane signaling may be signaling at a protocol stack and/or interfaceused for user data transmission. The signaling may be application layersignaling, or user plane signaling via one or more networks. Further, asused herein, control plane signaling may be signaling from anapplication entity to control plane network functions of one or morecore networks. In certain embodiments, the method 900 further comprisestransmitting a notification to the at least one vehicle-to-everythingapplication as feedback corresponding to the at least one applicationrequirement.

FIG. 10 is a flow chart diagram illustrating one embodiment of a method1000 for receiving application requirements for vehicle-to-everythingapplications. In some embodiments, the method 1000 is performed by anapparatus, such as the remote unit 102. In certain embodiments, themethod 1000 may be performed by a processor executing program code, forexample, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliaryprocessing unit, a FPGA, or the like.

In various embodiments, the method 1000 includes receiving 1002 at leastone application requirement from at least one vehicle-to-everythingapplication. In some embodiments, the method 1000 includes receiving1004 at least one provisioning parameter, wherein the at least oneprovisioning parameter is determined for a plurality ofvehicle-to-everything user equipments based on the at least oneapplication requirement, and the plurality of vehicle-to-everything userequipments are serviced by a plurality of communication networks.

In certain embodiments, the at least one application requirementcomprises a user equipment identifier, a radio parameter, a policyparameter, a public land mobile network identifier, a multiple publicland mobile network vehicle-to-everything service indication, a level ofcoordination, a level of granularity, a public land mobile networkpriority, a key performance indicator per vehicle-to-everything session,a quality of service per vehicle-to-everything session, an applicationto service mapping, a service area, a geographical area, assistanceinformation, a service to level of automation mapping, or somecombination thereof. In some embodiments, the at least onevehicle-to-everything application comprises a vehicle-to-everythingapplication server, a vehicle-to-everything application client of avehicle-to-everything user equipment of the plurality ofvehicle-to-everything user equipments, or a combination thereof.

In various embodiments, the at least one provisioning parametercomprises a radio parameter, a policy per radio access technology, aparameter per radio access technology, a policy for a long termevolution network, a policy for a new radio network, an access stratumlayer configuration, a time validity, a geographical area, a multiplepublic land mobile network vehicle-to-everything service flag, amultiple public land mobile network vehicle-to-everything servicenotification, a resource pool configuration per vehicle-to-everythingservice type, a resource pool configuration per vehicle-to-everythinggeographical area, a radio parameter for joint utilization per multiplepublic land mobile network vehicle-to-everything service, a list ofavailable quality indicators per public land mobile network, a qualityof service mapping configuration, an allowed public land mobile networklist and capabilities for joint radio resource utilization, a publicland mobile network priority over joint resources, a service-to-level ofautomation mapping, a delta parameter, a cause for provisioningadaptation, or some combination thereof. In one embodiment, the at leastone provisioning parameter comprises an initial configuration for theplurality of vehicle-to-everything user equipments.

In certain embodiments, the at least one provisioning parametercomprises an updated configuration for the plurality ofvehicle-to-everything user equipments. In some embodiments, the updatedconfiguration is triggered by an adaptation of the at least oneapplication requirement, a sidelink communication requirement, or acombination thereof. In various embodiments, the at least oneprovisioning parameter is provided to at least one application client.

In one embodiment, the at least one provisioning parameter is providedto the at least one communication network via user plane signaling,control plane signaling, or a combination thereof. In certainembodiments, the method 1000 further comprises transmitting the at leastone provisioning parameter to a vehicle-to-everything user equipment ofthe plurality of vehicle-to-everything user equipments. In someembodiments, the method 1000 further comprises performing processing onthe at least one application requirement, the at least one provisioningparameter, or a combination thereof.

In one embodiment, a method comprises: obtaining at least oneapplication requirement from at least one vehicle-to-everythingapplication; determining at least one provisioning parameter for aplurality of vehicle-to-everything user equipments based on the at leastone application requirement, wherein the plurality ofvehicle-to-everything user equipments are serviced by a plurality ofcommunication networks; and transmitting the at least one provisioningparameter to at least one vehicle-to-everything user equipment of theplurality of vehicle-to-everything user equipments, at least onecommunication network of the plurality of communication networks, orsome combination thereof.

In certain embodiments, the at least one application requirementcomprises a user equipment identifier, a radio parameter, a policyparameter, a public land mobile network identifier, a multiple publicland mobile network vehicle-to-everything service indication, a level ofcoordination, a level of granularity, a public land mobile networkpriority, a key performance indicator per vehicle-to-everything session,a quality of service per vehicle-to-everything session, anapplication-to-service mapping, a service area, a geographical area,assistance information, a service-to-level of automation mapping, orsome combination thereof.

In some embodiments, the at least one vehicle-to-everything applicationcomprises a vehicle-to-everything application server, avehicle-to-everything application client of a vehicle-to-everything userequipment of the plurality of vehicle-to-everything user equipments, ora combination thereof.

In various embodiments, the at least one provisioning parametercomprises a radio parameter, a policy per radio access technology, aparameter per radio access technology, a policy for a long termevolution network, a policy for a new radio network, an access stratumlayer configuration, a time validity, a geographical area, a multiplepublic land mobile network vehicle-to-everything service flag, amultiple public land mobile network vehicle-to-everything servicenotification, a resource pool configuration per vehicle-to-everythingservice type, a resource pool configuration per vehicle-to-everythinggeographical area, a radio parameter for joint utilization per multiplepublic land mobile network vehicle-to-everything service, a list ofavailable quality indicators per public land mobile network, a qualityof service mapping configuration, an allowed public land mobile networklist and capabilities for joint radio resource utilization, a publicland mobile network priority over joint resources, a service-to-level ofautomation mapping, a delta parameter, a cause for provisioningadaptation, or some combination thereof.

In one embodiment, the at least one provisioning parameter comprises aninitial configuration for the plurality of vehicle-to-everything userequipments.

In certain embodiments, the at least one provisioning parametercomprises an updated configuration for the plurality ofvehicle-to-everything user equipments.

In some embodiments, the updated configuration is triggered by anadaptation of the at least one application requirement, a sidelinkcommunication requirement, or a combination thereof.

In various embodiments, the at least one provisioning parameter isprovided to at least one application client of the at least onevehicle-to-everything user equipment.

In one embodiment, the at least one provisioning parameter is providedto the at least one communication network via user plane signaling,control plane signaling, or a combination thereof.

In certain embodiments, the method further comprises transmitting anotification to the at least one vehicle-to-everything application asfeedback corresponding to the at least one application requirement.

In one embodiment, an apparatus comprises: a processor that: obtains atleast one application requirement from at least onevehicle-to-everything application; and determines at least oneprovisioning parameter for a plurality of vehicle-to-everything userequipments based on the at least one application requirement, whereinthe plurality of vehicle-to-everything user equipments are serviced by aplurality of communication networks; and a transmitter that transmitsthe at least one provisioning parameter to at least onevehicle-to-everything user equipment of the plurality ofvehicle-to-everything user equipments, at least one communicationnetwork of the plurality of communication networks, or some combinationthereof.

In certain embodiments, the at least one application requirementcomprises a user equipment identifier, a radio parameter, a policyparameter, a public land mobile network identifier, a multiple publicland mobile network vehicle-to-everything service indication, a level ofcoordination, a level of granularity, a public land mobile networkpriority, a key performance indicator per vehicle-to-everything session,a quality of service per vehicle-to-everything session, an applicationto service mapping, a service area, a geographical area, assistanceinformation, a service to level of automation mapping, or somecombination thereof.

In some embodiments, the at least one vehicle-to-everything applicationcomprises a vehicle-to-everything application server, avehicle-to-everything application client of a vehicle-to-everything userequipment of the plurality of vehicle-to-everything user equipments, ora combination thereof.

In various embodiments, the at least one provisioning parametercomprises a radio parameter, a policy per radio access technology, aparameter per radio access technology, a policy for a long termevolution network, a policy for a new radio network, an access stratumlayer configuration, a time validity, a geographical area, a multiplepublic land mobile network vehicle-to-everything service flag, amultiple public land mobile network vehicle-to-everything servicenotification, a resource pool configuration per vehicle-to-everythingservice type, a resource pool configuration per vehicle-to-everythinggeographical area, a radio parameter for joint utilization per multiplepublic land mobile network vehicle-to-everything service, a list ofavailable quality indicators per public land mobile network, a qualityof service mapping configuration, an allowed public land mobile networklist and capabilities for joint radio resource utilization, a publicland mobile network priority over joint resources, a service to level ofautomation mapping, a delta parameter, a cause for provisioningadaptation, or some combination thereof.

In one embodiment, the at least one provisioning parameter comprises aninitial configuration for the plurality of vehicle-to-everything userequipments.

In certain embodiments, the at least one provisioning parametercomprises an updated configuration for the plurality ofvehicle-to-everything user equipments.

In some embodiments, the updated configuration is triggered by anadaptation of the at least one application requirement, a sidelinkcommunication requirement, or a combination thereof.

In various embodiments, the at least one provisioning parameter isprovided to at least one application client of the at least onevehicle-to-everything user equipment.

In one embodiment, the at least one provisioning parameter is providedto the at least one communication network via user plane signaling,control plane signaling, or a combination thereof.

In certain embodiments, the transmitter transmits a notification to theat least one vehicle-to-everything application as feedback correspondingto the at least one application requirement.

In one embodiment, a method comprises: receiving at least oneapplication requirement from at least one vehicle-to-everythingapplication; and receiving at least one provisioning parameter, whereinthe at least one provisioning parameter is determined for a plurality ofvehicle-to-everything user equipments based on the at least oneapplication requirement, and the plurality of vehicle-to-everything userequipments are serviced by a plurality of communication networks.

In certain embodiments, the at least one application requirementcomprises a user equipment identifier, a radio parameter, a policyparameter, a public land mobile network identifier, a multiple publicland mobile network vehicle-to-everything service indication, a level ofcoordination, a level of granularity, a public land mobile networkpriority, a key performance indicator per vehicle-to-everything session,a quality of service per vehicle-to-everything session, an applicationto service mapping, a service area, a geographical area, assistanceinformation, a service to level of automation mapping, or somecombination thereof.

In some embodiments, the at least one vehicle-to-everything applicationcomprises a vehicle-to-everything application server, avehicle-to-everything application client of a vehicle-to-everything userequipment of the plurality of vehicle-to-everything user equipments, ora combination thereof.

In various embodiments, the at least one provisioning parametercomprises a radio parameter, a policy per radio access technology, aparameter per radio access technology, a policy for a long termevolution network, a policy for a new radio network, an access stratumlayer configuration, a time validity, a geographical area, a multiplepublic land mobile network vehicle-to-everything service flag, amultiple public land mobile network vehicle-to-everything servicenotification, a resource pool configuration per vehicle-to-everythingservice type, a resource pool configuration per vehicle-to-everythinggeographical area, a radio parameter for joint utilization per multiplepublic land mobile network vehicle-to-everything service, a list ofavailable quality indicators per public land mobile network, a qualityof service mapping configuration, an allowed public land mobile networklist and capabilities for joint radio resource utilization, a publicland mobile network priority over joint resources, a service-to-level ofautomation mapping, a delta parameter, a cause for provisioningadaptation, or some combination thereof.

In one embodiment, the at least one provisioning parameter comprises aninitial configuration for the plurality of vehicle-to-everything userequipments.

In certain embodiments, the at least one provisioning parametercomprises an updated configuration for the plurality ofvehicle-to-everything user equipments.

In some embodiments, the updated configuration is triggered by anadaptation of the at least one application requirement, a sidelinkcommunication requirement, or a combination thereof.

In various embodiments, the at least one provisioning parameter isprovided to at least one application client.

In one embodiment, the at least one provisioning parameter is providedto the at least one communication network via user plane signaling,control plane signaling, or a combination thereof.

In certain embodiments, the method further comprises transmitting the atleast one provisioning parameter to a vehicle-to-everything userequipment of the plurality of vehicle-to-everything user equipments.

In some embodiments, the method further comprises performing processingon the at least one application requirement, the at least oneprovisioning parameter, or a combination thereof.

In one embodiment, an apparatus comprises: a receiver that: receives atleast one application requirement from at least onevehicle-to-everything application; and receives at least oneprovisioning parameter, wherein the at least one provisioning parameteris determined for a plurality of vehicle-to-everything user equipmentsbased on the at least one application requirement, and the plurality ofvehicle-to-everything user equipments are serviced by a plurality ofcommunication networks.

In certain embodiments, the at least one application requirementcomprises a user equipment identifier, a radio parameter, a policyparameter, a public land mobile network identifier, a multiple publicland mobile network vehicle-to-everything service indication, a level ofcoordination, a level of granularity, a public land mobile networkpriority, a key performance indicator per vehicle-to-everything session,a quality of service per vehicle-to-everything session, an applicationto service mapping, a service area, a geographical area, assistanceinformation, a service to level of automation mapping, or somecombination thereof.

In some embodiments, the at least one vehicle-to-everything applicationcomprises a vehicle-to-everything application server, avehicle-to-everything application client of a vehicle-to-everything userequipment of the plurality of vehicle-to-everything user equipments, ora combination thereof.

In various embodiments, the at least one provisioning parametercomprises a radio parameter, a policy per radio access technology, aparameter per radio access technology, a policy for a long termevolution network, a policy for a new radio network, an access stratumlayer configuration, a time validity, a geographical area, a multiplepublic land mobile network vehicle-to-everything service flag, amultiple public land mobile network vehicle-to-everything servicenotification, a resource pool configuration per vehicle-to-everythingservice type, a resource pool configuration per vehicle-to-everythinggeographical area, a radio parameter for joint utilization per multiplepublic land mobile network vehicle-to-everything service, a list ofavailable quality indicators per public land mobile network, a qualityof service mapping configuration, an allowed public land mobile networklist and capabilities for joint radio resource utilization, a publicland mobile network priority over joint resources, a service to level ofautomation mapping, a delta parameter, a cause for provisioningadaptation, or some combination thereof.

In one embodiment, the at least one provisioning parameter comprises aninitial configuration for the plurality of vehicle-to-everything userequipments.

In certain embodiments, the at least one provisioning parametercomprises an updated configuration for the plurality ofvehicle-to-everything user equipments.

In some embodiments, the updated configuration is triggered by anadaptation of the at least one application requirement, a sidelinkcommunication requirement, or a combination thereof.

In various embodiments, the at least one provisioning parameter isprovided to at least one application client.

In one embodiment, the at least one provisioning parameter is providedto the at least one communication network via user plane signaling,control plane signaling, or a combination thereof.

In certain embodiments, the apparatus further comprises a transmitterthat transmits the at least one provisioning parameter to avehicle-to-everything user equipment of the plurality ofvehicle-to-everything user equipments.

In some embodiments, the apparatus further comprises a processor thatperforms processing on the at least one application requirement, the atleast one provisioning parameter, or a combination thereof.

Embodiments may be practiced in other specific forms. The describedembodiments are to be considered in all respects only as illustrativeand not restrictive. The scope of the invention is, therefore, indicatedby the appended claims rather than by the foregoing description. Allchanges which come within the meaning and range of equivalency of theclaims are to be embraced within their scope.

1. A method at a device, the method comprising: receiving at least oneapplication requirement from at least one vehicle-to-everythingapplication; receiving at least one provisioning parameter, wherein theat least one provisioning parameter is determined for a plurality ofvehicle-to-everything user equipments based on the at least oneapplication requirement, and the plurality of vehicle-to-everything userequipments are serviced by a plurality of public land mobile networks(PLMNs); performing processing on the at least one applicationrequirement, the at least one provisioning parameter, or a combinationthereof; and transmitting the at least one provisioning parameter to avehicle-to-everything user equipment of the plurality ofvehicle-to-everything user equipments.
 2. The method of claim 1, whereinthe at least one application requirement comprises a user equipmentidentifier, a radio parameter, a policy parameter, a public land mobilenetwork identifier, a multiple public land mobile networkvehicle-to-everything service indication, a level of coordination, alevel of granularity, a public land mobile network priority, a keyperformance indicator per vehicle-to-everything session, a quality ofservice per vehicle-to-everything session, an application to servicemapping, a service area, a geographical area, assistance information, aservice to level of automation mapping, or some combination thereof. 3.The method of claim 1, wherein the at least one vehicle-to-everythingapplication comprises a vehicle-to-everything application server, avehicle-to-everything application client of a vehicle-to-everything userequipment of the plurality of vehicle-to-everything user equipments, ora combination thereof.
 4. The method of claim 1, wherein the at leastone provisioning parameter comprises a radio parameter, a policy perradio access technology, a parameter per radio access technology, apolicy for a long term evolution network, a policy for a new radionetwork, an access stratum layer configuration, a time validity, ageographical area, a multiple public land mobile networkvehicle-to-everything service flag, a multiple public land mobilenetwork vehicle-to-everything service notification, a resource poolconfiguration per vehicle-to-everything service type, a resource poolconfiguration per vehicle-to-everything geographical area, a radioparameter for joint utilization per multiple public land mobile networkvehicle-to-everything service, a list of available quality indicatorsper public land mobile network, a quality of service mappingconfiguration, an allowed public land mobile network list andcapabilities for joint radio resource utilization, a public land mobilenetwork priority over joint resources, a service-to-level of automationmapping, a delta parameter, a cause for provisioning adaptation, or somecombination thereof.
 5. The method of claim 1, wherein the at least oneprovisioning parameter comprises an initial configuration for theplurality of vehicle-to-everything user equipments.
 6. The method ofclaim 1, wherein the at least one provisioning parameter comprises anupdated configuration for the plurality of vehicle-to-everything userequipments.
 7. The method of claim 6, wherein the updated configurationis triggered by an adaptation of the at least one applicationrequirement, a sidelink communication requirement, or a combinationthereof.
 8. The method of claim 1, wherein the at least one provisioningparameter is provided to at least one application client.
 9. The methodof claim 1, wherein the at least one provisioning parameter is providedto the at least one PLMN via user plane signaling, control planesignaling, or a combination thereof.
 10. (canceled)
 11. (canceled) 12.An apparatus for wireless communication, the apparatus comprising: aprocessor; and a memory coupled to the processor, the processorconfigured to cause the apparatus to: receive at least one applicationrequirement from at least one vehicle-to-everything application; receiveat least one provisioning parameter, wherein the at least oneprovisioning parameter is determined for a plurality ofvehicle-to-everything user equipments based on the at least oneapplication requirement, and the plurality of vehicle-to-everything userequipments are serviced by a plurality of public land mobile networks(PLMNs); perform processing on the at least one application requirement,the at least one provisioning parameter, or a combination thereof; andtransmit the at least one provisioning parameter to avehicle-to-everything user equipment of the plurality ofvehicle-to-everything user equipments.
 13. The apparatus of claim 12,wherein the at least one application requirement comprises a userequipment identifier, a radio parameter, a policy parameter, a publicland mobile network identifier, a multiple public land mobile networkvehicle-to-everything service indication, a level of coordination, alevel of granularity, a public land mobile network priority, a keyperformance indicator per vehicle-to-everything session, a quality ofservice per vehicle-to-everything session, an application to servicemapping, a service area, a geographical area, assistance information, aservice to level of automation mapping, or some combination thereof. 14.The apparatus of claim 12, wherein the at least onevehicle-to-everything application comprises a vehicle-to-everythingapplication server, a vehicle-to-everything application client of avehicle-to-everything user equipment of the plurality ofvehicle-to-everything user equipments, or a combination thereof.
 15. Theapparatus of claim 12, wherein the at least one provisioning parametercomprises a radio parameter, a policy per radio access technology, aparameter per radio access technology, a policy for a long termevolution network, a policy for a new radio network, an access stratumlayer configuration, a time validity, a geographical area, a multiplepublic land mobile network vehicle-to-everything service flag, amultiple public land mobile network vehicle-to-everything servicenotification, a resource pool configuration per vehicle-to-everythingservice type, a resource pool configuration per vehicle-to-everythinggeographical area, a radio parameter for joint utilization per multiplepublic land mobile network vehicle-to-everything service, a list ofavailable quality indicators per public land mobile network, a qualityof service mapping configuration, an allowed public land mobile networklist and capabilities for joint radio resource utilization, a publicland mobile network priority over joint resources, a service to level ofautomation mapping, a delta parameter, a cause for provisioningadaptation, or some combination thereof.
 16. The apparatus of claim 12,wherein the at least one provisioning parameter comprises an initialconfiguration for the plurality of vehicle-to-everything userequipments.
 17. The apparatus of claim 12, wherein the at least oneprovisioning parameter comprises an updated configuration for theplurality of vehicle-to-everything user equipments.
 18. The apparatus ofclaim 17, wherein the updated configuration is triggered by anadaptation of the at least one application requirement, a sidelinkcommunication requirement, or a combination thereof.
 19. The apparatusof claim 12, wherein the at least one provisioning parameter is providedto at least one application client.
 20. The apparatus of claim 12,wherein the at least one provisioning parameter is provided to the atleast one PLMN via user plane signaling, control plane signaling, or acombination thereof.
 21. (canceled)
 22. (canceled)